o/snapstate: prevent removal of seed-refresh snaps when seed-refresh is enabled - #16952
Conversation
|
Mon Jun 1 14:13:32 UTC 2026 Failures:Executing:
Skipped tests from snapd-testing-skipIf you wish to have any of the below tests run in your PR, in your PR description, add 'unskip:' followed by a copy-and-pasted list (without variants) of the below tests you wish to run (unskip plus test list must be valid yaml)
|
97e87f7 to
30bea64
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #16952 +/- ##
==========================================
- Coverage 78.99% 78.99% -0.01%
==========================================
Files 1378 1376 -2
Lines 192017 192101 +84
Branches 2464 2464
==========================================
+ Hits 151681 151743 +62
- Misses 31185 31207 +22
Partials 9151 9151
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3bfd63f to
4a527b7
Compare
4a527b7 to
7f2902d
Compare
9864a78 to
842a4f9
Compare
| // | ||
| // TODO:SEEDREFRESH: remove this hook once seed-refresh supports seeds | ||
| // gaining/losing snaps | ||
| var CheckSeedRefreshRemove = func(st *state.State, si *snap.Info, dctx DeviceContext) error { |
There was a problem hiding this comment.
Adding this does feel lame, but at least it is temporary?
842a4f9 to
b126617
Compare
Since seed-refresh doesn't support adding/losing snaps from the seed, we need to ensure that the running system always has the snaps that are a part of the seed.